🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf 'Workflow file:\n'
if [ -f .github/workflows/release-nightly.yml ]; then
  cat -n .github/workflows/release-nightly.yml | sed -n '1,80p'
else
  echo 'missing'
fi

printf '\nOther workflow concurrency snippets:\n'
rg -n "concurrency:|queue:|cancel-in-progress:" .github/workflows || true

printf '\nCurrent workflow trigger summary:\n'
python3 - <<'PY'
from pathlib import Path
p=Path('.github/workflows/release-nightly.yml')
if not p.exists():
    print('missing')
    raise SystemExit
for i,line in enumerate(p.read_text().splitlines(),1):
    if i<=40 and any(s in line for s in ['on:', 'workflow_dispatch', 'push', 'schedule', 'concurrency']):
        print(f'{i}: {line}')
PY

Repository: nuxt/image

Length of output: 3118

🌐 Web query:

GitHub Actions concurrency queue max behavior pending runs cancel-in-progress false

💡 Result:

In GitHub Actions, the behavior of a concurrency group when cancel-in-progress is false depends entirely on whether you are using the default single-queue behavior or the recently introduced extended queuing capability [1][2]. Default Behavior (Implicit queue: single) When you set cancel-in-progress: false (or omit it, as it defaults to false), GitHub Actions allows at most one job or workflow to be running and one to be in a pending state [1][3]. - If a new run is triggered while one is already running, it becomes the single pending run [3][4]. - If a subsequent (third) run is triggered while another is already pending, the existing pending run is canceled and replaced by the new run [1][4]. - This ensures that only the most recently triggered run is waiting to execute next, while the currently running job completes [4]. Extended Queuing Behavior (queue: max) As of May 2026, you can opt into a larger queue by setting queue: max in your concurrency block [2]. - This allows up to 100 jobs or workflow runs to be queued in a pending state within the same concurrency group [1][5]. - Runs are processed sequentially in the order they were queued [1][2]. - When the queue reaches its limit of 100, any additional incoming runs are canceled [1][5]. Important Constraints - You cannot combine queue: max with cancel-in-progress: true; doing so will result in a workflow validation error because they represent conflicting strategies for handling concurrent runs [1][6]. - The default behavior (queue: single) is essentially a queue of size 1 where new entries force the eviction of older ones [1][4]. The queue: max option allows for a true first-in-first-out (FIFO) queue for up to 100 items [1][2].

Citations:

• 1: https://docs.github.com/actions/writing-workflows/choosing-what-your-workflow-does/control-the-concurrency-of-workflows-and-jobs
• 2: https://github.blog/changelog/2026-05-07-github-actions-concurrency-groups-now-allow-larger-queues/
• 3: Clarify concurrency cancel-in-progress behaviour github/docs#30647
• 4: https://stackoverflow.com/questions/76096372/how-to-queue-more-than-one-github-action-workflow-run
• 5: https://docs.github.com/en/actions/reference/limits
• 6: https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.